home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Belgian Amiga Club - ADF Collection
/
BS1 part 26.zip
/
BS1 part 26
/
Powervisor v1.10b disk1.adf
/
pv.bugs
< prev
next >
Wrap
Text File
|
1991-09-30
|
4KB
|
78 lines
Bugs
symbols I think something is wrong with symbols because some
people reported strange behaviour. I can't find the
bug, so maybe it was caused by something else. Maybe
the bug is even solved :-)
locks Break... is not printed when we interrupt the lock listing
This harmless bug is a replacement for a memory loosing
bug. I prefer this bug :-)
Stack overflow There seem to be some problems with 'killing' a task
that has crashed because of a stack overflow
('account' command). The solution is of course not to
kill the program :-) PowerVisor has halted the program
so it will do no more (!) harm
Debugging Debugging (with 'debug l' and 'debug n') often causes
little memory loss. I know the reason so this will get
fixed very soon
Bugs for AmigaDOS 1.2/1.3 version of PowerVisor only
cursor The cursor in the stringgadget sometimes disappears in
the AmigaDOS 1.2/1.3 version of PowerVisor (this happens
the first time you use the <up> key to go in history)
stringgadget I know of no way to unactivate a stringgadget in AmigaDOS
1.3 and older. Therefore cycling through the windows
with <tab> is not enough to deactivate the stringgadget.
You will have to press <enter> first (or click next to
the stringgadget) before you can press the key (with
-MORE- or -HALT-)
Things that could be better and maybe should be supported
mmu 'mmutree' does not support indirect pages and 8 byte
descriptors
'mmutree' does not support FC trees (function codes)
signals maybe we should share some signals, we have only five
signals left
'mode' The mode variable is not restored when an error occurs
while assigning to 'mode'
disp 1a should give an error
trace u PowerVisor may disturb other programs if you set your
breakpoint in shared memory
free The Free function should check if the memory you
try to free is OK
trace Tracing is very hazardous for multitasking. You can
scarcely move your mouse
crashes There are still some guru's PowerVisor does not trap
crash trapping Address Errors are not recoverable
fonts We should not permit proportional fonts
search/copy/fill
These routines are very sensitive to bad arguments
(negative for example)
Overflows Powervisor does not always check for overflow (especially
with string parsing) Make sure that your string are always
smaller than the maximum line length in the stringgadget
(set with 'prefs linelen', default 400)
Future enhancements (note that these are NOT promises :-)
owner Owner should be expanded to handle more system lists
load Load must have an extra argument : offset to start loading
customize I plan to make a seperate file containing all command
strings, function strings and some other strings. That way
the user will be able to customize PowerVisor by changing
this file. This file will not be resident in memory.
PowerVisor will build internal data structures using this
file
pvcall Instead of only one command for each installable post or
pre command I plan to incorporate a list system (see the
TheWizardCorner file for the 'pvcall' command)
mmu I have been thinking about a very powerful system to
use the mmu for protecting memory. PowerVisor could be
protected from other programs and some extra commands
could be provided to read or write protect regions
of memory